Test Results

 2 files  ±0   6 suites  ±0   8m 21s ⏱️ ±0s
20 tests ±0  20 ✅ ±0  0 💤 ±0  0 ❌ ±0 
64 runs  ±0  64 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 8ab36e3. ± Comparison against base commit 3efac67.

Test jobs for commit 8ab36e3

• Job 110629 on qcs6490
• Job 110628 on qrb2210-rb1

IIUC meta-qcom is on 00103.0: https://github.com/qualcomm-linux/meta-qcom/tree/master/recipes-bsp/firmware-boot

Do you think it would make sense to stay aligned, for less painful development and debugging of related issues on both sides? For bonus points, maybe we can automatically have one follow the other :-)

Otherwise, this looks fine.

IIUC meta-qcom is on 00103.0: https://github.com/qualcomm-linux/meta-qcom/tree/master/recipes-bsp/firmware-boot

Do you think it would make sense to stay aligned, for less painful development and debugging of related issues on both sides? For bonus points, maybe we can automatically have one follow the other :-)

Otherwise, this looks fine.

That's a good point! We have enough on our plate, but I guess I'm also too proud to consider ourselves second class citizens downstream of meta-qcom haha

We can keep this open until meta-qcom updates or something; one thing I haven't done here is digging up changes from the past firmware releases, that would be good input for us on what kind of issues to look for when taking these updates